Subject: ADC requirements

From: "Hildebrand, Jeff" <[email-masked]>
Date: Thu, 05 May 94 23:08:00 PDT

Larry Fisher & I sat down and built what we consider to
be a base set ADC requirements.  This exercise showed me
how my focus had become too implementation oriented, and
allowed me to take a different perspective.

Requirements:

1. There are no restrictions on the type of data that can
be transferred across the network.

2. Since the OSI/TP CRM makes no distinction between
initialization data and regular data, except when they
are sent, both need to be convertible.

3. No known requirement exists for expedited data to be
convertible, at this time.

4. The user supplied converter* software needs to be able
to be hooked into the CRM below the CPIC layer, and able
to convert the data stream:
     A. Prior to CPIC handing it to the CPIC Transaction
          program upon receipt.
     B. Prior to going out to the partner node upon a
          CPIC transaction program send.

5. The converter software must be separate from the CPIC
transaction program, and reusable by multiple programs.

6. No restrictions are placed on the converter's
functionality.  Any restrictions are the result of a
particular implementor's implementation.

Regards,
jeff

* A converter is a user written software routine that is
called by the system to manipulate user data in a user
specified manner.  One of the recognized uses for a
converter is to apply ASN.1 or other user defined
encoding/decoding to user data.

---

From: "Hildebrand, Jeff" <[email-masked]>
Date: Thu, 12 May 94 11:01:00 PDT

----------
From: DATCON/DCCORP/JohnD
To: jeffh
Subject: ADC Requirements
Date: Thursday, May 12, 1994 10:49AM

Jeff,

With reference to your email dated 5-12-94, I have no problems with your
list of requirements.

Regards

JohnD.